These fields control the properties of content folders that are defined in the system. By default, these fields are found in the following locations:
■ Content Management > Content designer > Manage content, then from the Document System toolbar choose New > Website Content Folder (or select an existing content folder, then from the toolbar choose Edit).
Note: The iMIS content folder and all of its descendant content folders and content records are protected for use by iMIS. The default Document System permissions for these content folders and content records permit editing only by members of the SysAdmin role.
Status
Specifies whether this definition object is in a Working, PublishPending, Submitted, Published, Inactive, or Active state. Click the expand icon to view further details, including who created the record, who modified it last, and dates of these changes.
■ Content records in a Working state have been saved within the iMIS database, but the latest changes have not been made active on the associated CM websites by the associated publishing servers and their corresponding iMIS publishing service (AsiPublishing15). The Publish command on the toolbar queues the content record to the associated publishing servers, during which the content record is in a PublishPending state and can be viewed in the Pending Requests detail for the associated publishing servers. After each publishing server has successfully processed the publishing request, the latest changes become visible on the associated websites and become active within iMIS, both of which are denoted by the Published state.
If an iMIS user does not have content authority group (CAG) Content Approver permissions, they will see a Submit command instead of a Publish command. The Submit command queues a publishing request to the Content Designer Task List of all CAG members who have Content Approver permissions. (Alternatively, if workflow is enabled for the parent content folder, only those members of the content folder's assigned CAG who have Content Approver permissions.) Only a person with Content Approver permissions in at least one CAG can actually publish content records.
■ For all other definition objects, the publishing process is less complex and does not involve CAG permissions, publishing servers, or the iMIS publishing service. When the object is in a Working state, the latest changes have been saved within the iMIS database, but they have not yet been made active within iMIS. The Publish command makes the latest changes active within iMIS.
■ Websites in an Inactive state are offline so that browsers cannot view the website content, and instead see a 503 error (Service Unavailable) from IIS. Selecting the Is this website active? checkbox in the Status section of the website's definition puts the website in an Active state, enabling browsers to view the website content. Clearing the checkbox puts the website in an Inactive state.
Folder Name
Specifies a version of the folder Title that meets the requirements for an IIS path segment to the rendered .aspx files for each content record in the folder. Every content folder created in CM has a corresponding IIS folder.
Default Website (for search)
Specifies the website for which searches will always include the content records within this content folder. This value is not inherited by any children content folders, although when you create a new content folder this field will copy the current value from its parent content folder as a default value.
Troubleshooting: If iMIS returns no search results, be sure to designate some content folders to list the specific website in either of these fields.
Include content in Searches for these additional Websites
Specifies additional websites, other than the one specified in Default Website (for search), for which searches will always include the content records within this content folder. These values are not inherited by any children content folders, although when you create a new content folder this field will copy the current values from its parent content folder as default values.
Caution! If you clear the Always display content in default website checkbox, be careful to specify only additional websites whose sitemaps include navigation items that link to all of the content records in this content folder.
Troubleshooting: If iMIS returns no search results, be sure to designate some content folders to list the specific website in either of these fields.
Always display content in default website
Displays the rendered version of a content record in this content folder in the context of the website specified in Default Website (for search) regardless of which website the search was performed on. When cleared, displays the rendered content record in the context of the website in which the search was made.
Publish on Servers
Specifies the publishing servers that should manage the publishing of all content records within this content folder.
■ In the simplest case where you have only one publishing server defined in your CM environment, you should set this value to All for the root content folder (@) and set this value to Inherit on all folders beneath the root.
■ In more complex environments with multiple publishing servers, you should generally use the Custom option to select one or more specific publishing servers for a given content folder and then set this value to Inherit on all folders beneath the one for which you chose a custom selection of publishing servers.
Workflow Management
Specifies whether content workflow is enabled for this content folder (and by default, all of its children content records too).
■ If an Authority Group is assigned to this folder, then content workflow is enabled, and only the members of that content authority group (CAG) receive workflow notifications in their Content Designer Task List when changes occur to content records in the content folder.
■ If no Authority Group is assigned, then any member of any CAG in the system receives workflow notifications in their task list when changes occur to content records in the content folder.
The following fields appear only when a CAG is assigned to a content folder.
■ Owner of this content - Specifies which member of the assigned CAG should replace the designated content owner of any child content records or content folders if the current owner assigned to a content record becomes ineligible for any reason. The drop-down list includes only those members of the assigned CAG who have Content Editor permissions.
■ Content is considered expired n days after last published - Specifies the default expiration interval for all content records in this folder. Expired content records are no longer rendered on CM websites, but the content record remains in the system with no change in status until it is manually deleted by using the Organize > Delete command on the Document System toolbar or by using the Delete Selected button on a CAG member's Content Designer Task List. (This default expiration behavior can be selectively overridden by the Automatically delete expired content? field in the definition of each content record.) Manually republishing the content record makes it appear again on the CM websites and resets the expiration interval.
The expiration interval can be effectively overridden for a specific content record in this folder by specifying a value smaller than the expiration interval for the Automatic Publishing Frequency field in the content record definition. This ensures that the expiration interval is never reached for that content record.
■ Update this value for content in this folder and all subfolders - Automatically applies the settings in this Workflow Management section to all descendant content folders when you save your changes to this content folder definition.
Current tags
Specifies the tags that are currently associated with this content folder. Clicking the Modify link displays a tag selection tree. Tags applied to a content folder are inherited by all descendant content records and content folders, not just the immediate children of this content folder. The Tags inherited from parent hierarchy area lists all tags that are being inherited from a content folder higher in the content folder hierarchy.
Only the inherited tags and the additional specific tags that you select here are used by the CM search engine. If you want search results to also find the descendant content records by descendant tags in the tag hierarchy, you must select the parent tag and also the specific descendant tags.
Although the CM search engine recognizes tag inheritance and finds descendant content records based on inherited tags, the Items by Tag report does not recognize tag inheritance and won't list the descendant content records and content folders for a tag that they inherit.
To choose useful tags for the dynamic handling of descendant content records, it helps to understand how tag-related functionality handles tag inheritance.
□ The pre-filtered result set of a basic or advanced search includes all published content records that are tagged with any descendant of the tag that is matched by the search keywords.
□ The pre-filtered result set of an advanced search includes all published content records that are tagged with any descendant of a tag that is specified in the configuration of the AdvancedSearch iPart if the user selects that tag at runtime on the rendered page that contains the advanced search form.
□ The pre-filtered result set of a rendered ContentTaggedList iPart also includes published content records that are tagged with any descendent of a tag that is specified in the configuration of the ContentTaggedList.
□ The content of the Items by Tag report (in Content Management > Reports) does not list published content records that are tagged with any descendant of each tag in the report.
Note: Tags are always overwritten on import. For example, if you import a content folder from a staging server to a production server, the assigned tags on the production server are overwritten by whatever tags were assigned on the staging server.
Access Settings
Specifies the Document System permissions granted for this definition object to iMIS security roles, security groups, specific iMIS users, iMIS member types, or to all Full and Casual users based on their assigned authorization levels.
■ Apply changes to all descendants - Changes to this section, when saved, flow automatically to all descendant definition objects. When cleared, changes to this section apply only to the current definition object. This checkbox usually appears only on Document System folder objects.
■ Use a preconfigured security set - Specifies a preconfigured security configuration to use for this definition object, which can be much simpler than using the Make this available to option to specify the permissions for definition objects. The specific permissions in the preconfigured security configuration are displayed (read-only) in the Make this available to area.
If you select a preconfigured security configuration and then switch to the Make this available to option, the permissions granted by the preconfigured security configuration are copied. This enables you to use a preconfigured security configuration as a starting point for defining custom permissions.
■ Make this available to - Lists the roles, groups, users, member types, or authorization levels that have been enabled to define or view rendered output from this object. This option enables you to specify custom permissions for the definition object if none of the preconfigured security configurations meets your needs. The SysAdmin, Content Administrator, and Everyone roles are default system-defined security roles that are assigned to every definition object used by CM. The SysAdmin role is assigned in the definition of an iMIS user record, but the Content Administrator role is automatically assigned to every iMIS user who is a member of a CM content authority group (CAG) that is designated as a Master Admin CAG.
The permissions that can be assigned to each entry in the list are:
□ Full Control - Enables all of the following permissions.
□ Read - Enables users to see this object both in CM definition windows and as rendered output in CM websites, but they cannot change the object's definition.
□ Add - Enables users to create new objects, or to paste or import an object into the Document System.
□ Edit - Enables users to edit this object's definition, but not to delete the object.
□ Delete - Enables users to delete this object.
□ Select – (if displayed) Enables users to assign a tag to content folders and content records.